Note: Where you see local paths specified, be sure to use the path appropriate for your system, such as C:\Program Files (x86)\ for C:\Program Files\.
Note: The following procedure uses the specific name ASI_2 to represent the root folder of your second instance of iMIS. Substitute the actual name of the root folder of your second instance.
1. Delete all of the files from the ASI_2 folder structure that comprises your second instance of iMIS.
2. Apply the update release to your original instance of iMIS first, following the instructions in the update release notes.
3. Copy the contents of your updated ASI folder structure from your original instance and modify the access control lists.
□ Copy the entire contents of the ASI folder (your original instance of iMIS) and all of its sub-folders into the ASI_2 folder.
□ Modify the access control lists for the new folder by running the following from a command line against that folder:
ICACLS "Program Files\ASI_2" /t /grant Users:F
ICACLS "Program Files\ASI_2\iMIS\Net" /t /grant "Network Service":F
4. Run iMIS DB Upgrader on the database used by the second instance.
□ Locate and run the DBUpgrader.exe utility that is located in the ASI_2 folder structure (C:\Program Files\ASI_2\iMIS\net\iMISDBUpgrade).
Caution! Do not launch iMIS DB Upgrader from the Start menu: that shortcut launches the utility associated with your original instance of iMIS.
□ Specify the location of the iMIS database used for the second instance of iMIS and the password for the iMIS SQL Server login on that SQL Server instance.
□ Click Begin Upgrade. The message Upgrade Completed appears at the bottom of the window when the upgrade completes.
□ Click Exit Upgrade.
5. Run the Multi-Instance Utility, AsiMultiInstanceUtility.exe, specifying the path, virtual directory, and so forth for the second instance in the same way as for a new second instance.
6. Disable Configure Services (uncheck for patches); this leaves existing Workflow, Publishing, and Index Catalog services in place for the second instance.
7. Click Reconfigure iMIS site. The utility displays status information as it updates .config files, updates the SystemConfig table in the database, and creates an ODBC DSN entry for the new database instance. The message Configuration Successful appears when it completes.
If reconfiguration stops and Remove Indexing Catalog is enabled, click it before proceeding. Once the conflicting Indexing Service catalog is removed, run Reconfigure iMIS site again. See Removing the indexing catalog (Indexing Service).
8. Test the upgraded second instance:
□ Log on to iMIS Desktop as MANAGER; from System Setup > iMIS management, ensure that the database, web server, and SMTP server information are correct for this second instance of iMIS.
□ Use a browser to test the other views of iMIS for this second instance.